Overview

Details

An Oracle database consists of several components: program files, configuration files, online and archived redo log files, control files, and database data files. To achieve a complete database backup, all of these components must be saved. Program and configuration files can be saved via a normal NetWorker backup. The others are backed up by Odtasm once properly configured.

The Oracle Database Toolkit is licensed to run on a single NetWorker backup server. The Version 2 package consists of an 8mm tape for either SunOS/Solaris or AIX/6000, product registration form and a hardcopy of the manpage. The tape contains the Odtasm executable along with the manpage and the Rawasm executable.

New Features in Version 2

• Simplified installation.
• No more shell scripts to configure.
• Automatic determination of tablespace datafiles.
• Automatic configuration of tablespace names.
• Support for cold, as well as hot backups.
• "In place" saves of control files on cold backups.
• "Incremental mode" for skipping tablespaces.

Prerequisites

• Odtasm only supports Oracle 7.1.x databases.
• While Odtasm supports a cold offline backup option, the database must be online when the backup is initiated to allow its configuration to be "probed".
• The database must be in ARCHIVELOG mode with automatic archiving enabled, otherwise an error occurs and the database backup will be terminated.
• Odtasm presently requires NetWorker 4.1x. NetWorker 4.0.2 is not supported.
• While Odtasm automates many aspects of database backup, database recoveries are not automated and require an experienced DBA.

Database Saves

• Odtasm is initiated with various settings by a NetWorker directive to backup a designated file (which will ultimately be used to contain a backup copy of the control file).
• Settings provided to odtasm must include the ORACLE_SID and ORACLE_HOME (specified as arguments to the -S and -H options), and may include options for cold backups and incrementals.
• Now invoked, odtasm queries the database to verify that it is operating in ARCHIVELOG mode with automatic archiving enabled, and to determine the location of the archived log files.
• If this is a full backup including datafiles, the database is queried for a list of all database files and their corresponding tablespace name.
• If this is a cold backup (-C option), the database is queried for the location of the control files, and the database is shutdown. A shutdown immediate is performed if the -F (force) option was selected.
• The datafiles for each tablespace are saved (if a full). If a hot backup, each tablespace save is bracketed by alter tablespace begin backup and end backup statements to place the tablespace in backup mode. Tablespaces are saved sequentially. Rawasm is used to backup raw partition data.
• In cold backup mode, the database control files are saved in place, and the database is restarted.
• In hot backup mode, a log switch is initiated. Odtasm monitors the database, waiting (a finite time) for the actual automatic archival to occur.
• Odtasm saves the archived log files.
• Odtasm extracts a copy of the online control file using an alter database backup controlfile statement to the file designated on the command line.
• Finally, Odtasm saves (using uasm) the extracted control file in its output stream.

Database Recovery

• The Odtasm program does not participate directly in recoveries. The datafiles, control files, and archived redo logs saved by odtasm are recovered using standard NetWorker recovery tools. Once these files are recovered by NetWorker, an Oracle recover can begin under the direction of the DBA.
• Note that during hot backups, the backup copy of the control file was saved under the filename supplied with the odtasm directive. For cold backups, the actual control files were saved in place.
• In general, starting up Oracle (with a good control file or control file copy) will cause Oracle to tell you the data files needing recovery, or those that cannot be found.
• Next, recover the datafiles/raw partitions identified by Oracle as missing.
• Finally, perform a tablespace or datafile Oracle recovery. This has various options, including one where Oracle will tell you the archived log files needing to be reapplied. These can be (NetWorker) recovered.
• Oracle provides details on database recovery in the ORACLE7 Server Administrator's Guide, Chapter 19. Page 19-7 has a good summary table.

Price and Availability

Order Information 		List Price 	Annual Software Subscription

8945  ODT for AIX/6000 		$6,000* 		$1,080*

8965  ODT for Solaris 		$6,000* 		$1,080*

Note that the optional Annual Software Subscription permits free telephone support and free software updates for one year. For more information, call Darrell Miller or John Siegel at 415/812-6000.

Free updates to customers under software subscription are automatically distributed.

Evaluating the Oracle Database Toolkit

Database Consulting Services

Consulting Charges

(Order Codes - List Prices) 	North American Locations 	Intl. Locations

First Database Server*		   #8901 - $4,000 		#8903 - $6,500

Subsequent DB Servers** (each)     #8902 - $1,000 		#8902 - $1,000

* Includes travel expenses.
** Accomplished during same installation engagement.

Legato Systems, Inc
3145 Porter Drive
Palo Alto, CA 94304
Voice: 415-812-6000 / Fax: 415-812-6032